Electronic fetal monitoring applications and display

ABSTRACT

Systems, methods, and computer-readable media are provided for displaying on a user display device alarm-triggering events detected by the medical device based on the location of the user display device. The method comprises receiving alarm-triggering patient data from a medical device and determining the physical location of first and second user display devices. The method further comprises determining that the physical location of the first user display device is designated to have an alarm displayed, and that the physical location of the second user display device is not designated to have an alarm displayed. In response to these determinations, the content of the alarm is displayed on the first user display device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application having attorney docket number CRNI.225116 and entitled“Electronic Fetal Monitoring Applications and Display” is a continuationapplication of co-pending U.S. patent application Ser. No. 12/564,569,filed Sep. 22, 2009 and entitled “Electronic Fetal MonitoringApplications and Display.” The entirety of the aforementionedapplication is incorporated by reference herein.

BACKGROUND

Electronic fetal monitoring (EFM) is the use of electronic fetalheart-rate monitoring for the evaluation of fetal well-being. EFMdevices are used during pregnancy, labor and birth in over 99% ofpatients. Clinicians base clinical decisions utilizing the waveforminformation produced by EFM devices. EFM devices may show fetal heartrate deceleration and acceleration patterns that are monitored byclinicians. Additional information such as heart rate, blood pressureand uterine pressure and contraction information may also be monitored.This information may be used by clinicians to determine if a fetus ishealthy or if medical intervention, such as delivery by surgicaloperation, is necessary.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to methods, systems andcomputer storage media having computer-executable instructions embodiedthereon that, when executed, cause a computing device to perform amethod of displaying waveform tracings for data received from one ormore medical devices. A first waveform tracing for data received fromone or more medical devices for a first individual is displayed. Asecond waveform tracing for data received from one or more medicaldevices for a second individual is displayed. In response to thedetermination to hide the first waveform tracing, only displaying secondwaveform tracing.

Embodiments of the present invention relate to methods, systems andcomputer storage media having computer-executable instructions embodiedthereon that, when executed, cause a computing device to perform amethod of displaying on a user device alarm-triggering events detectedby the medical device based on the location of the user device. Patientdata which triggers an alarm is received from a medical device. Thephysical location of first and second user display devices isdetermined. The physical location of the first and second user displaydevices is independent from the users logged onto the first and seconduser display devices. It is determined that the physical location of thefirst user display device is designated to have the alarm displayed. Itis determined that the physical location of the second user displaydevice is not designated to have the alarm displayed. In response to thedeterminations, the content of the alarm is displayed on the first userdisplay device and not the second user display device.

Embodiments of the present invention relate to methods, systems andcomputer storage media having computer-executable instructions embodiedthereon that, when executed, cause a computing device to perform amethod of displaying medical annotations for a patient. A first medicalannotation for a patient relating to one or more of the patient'sdemographic information, medical condition, or status is received from aclinician. A request not to display the first annotation whenannotations are displayed for the patient is received. The firstannotation for the patient and the request to hide the first annotationare stored in the patient's electronic medical record. Additionalmedical annotations are received and stored for the patient. A requestfrom to view medical annotations for the patient is received. The storedfirst annotation and additional annotations are accessed for thepatient. It is determined that the first annotation has been requestednot to be displayed. In response to the determination, the additionalpatient annotations are displayed but the first annotation for thepatient is not.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below with reference to the attacheddrawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing embodiments of the present invention;

FIG. 2 is an exemplary system architecture suitable for use inimplementing embodiments of the present invention;

FIG. 3 is an illustrative flow diagram of a method for displayingwaveform tracings from a medical device for two individuals, inaccordance with an embodiment of the present invention;

FIG. 4 is an illustrative screen display showing waveform tracings fromone or more medical devices, in accordance with an embodiment of thepresent invention;

FIG. 5 is an illustrative screen display showing waveform tracings fromone or more medical devices with at least one waveform disabled, inaccordance with an embodiment of the present invention;

FIG. 6 is an illustrative screen display showing waveform tracings formultiple fetuses, in accordance with an embodiment of the presentinvention;

FIG. 7 is an illustrative screen display showing waveform tracings fromone or more medical devices showing only one of multiple fetuses, inaccordance with an embodiment of the present invention;

FIG. 8 is an illustrative flow diagram of a method for simultaneouslydisplaying waveform tracings from one or more individuals and relatedmedical annotations, in accordance with an embodiment of the presentinvention;

FIG. 9 is an illustrative screen display for allowing a user to inputmedical annotations for a labor and delivery patient, in accordance withan embodiment of the present invention;

FIG. 10 is an illustrative screen display showing current and historicalwaveform tracings and textual annotations for a patient, in accordancewith an embodiment of the present invention;

FIG. 11 is an illustrative screen display showing a portion of awaveform tracing related to a medical annotation, in accordance with anembodiment of the present invention;

FIG. 12 is an illustrative flow diagram of a method for displayingalerts, in accordance with an embodiment of the present invention;

FIG. 13 is an illustrative screen display showing alerts and waveformtracings for multiple maternity patients, in accordance with anembodiment of the present invention;

FIG. 14 is an illustrative screen display showing waveform tracings formaternity patients satisfying alert conditions, in accordance with anembodiment of the present invention; and

FIG. 15 is an illustrative screen display showing the identification ofa portion of the waveform tracing for a patient being monitored, inaccordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies.

Having briefly described embodiments of the present invention, anexemplary operating environment suitable for use in implementingembodiments of the present invention is described below.

Referring to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, a medicalinformation computing system environment, with which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 20. It will be understood and appreciatedby those of ordinary skill in the art that the illustrated medicalinformation computing system environment 20 is merely an example of onesuitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of the invention.Neither should the medical information computing system environment 20be interpreted as having any dependency or requirement relating to anysingle component or combination of components illustrated therein.

The present invention may be operational with numerous other generalpurpose or special purpose computing system environments orconfigurations. Examples of well-known computing systems, environments,and/or configurations that may be suitable for use with the presentinvention include, by way of example only, personal computers, servercomputers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

The present invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include, but are notlimited to, routines, programs, objects, components, and data structuresthat perform particular tasks or implement particular abstract datatypes. The present invention may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inassociation with local and/or remote computer storage media including,by way of example only, memory storage devices.

With continued reference to FIG. 1, the exemplary medical informationcomputing system environment 20 includes a general purpose computingdevice in the form of a control server 22. Components of the controlserver 22 may include, without limitation, a processing unit, internalsystem memory, and a suitable system bus for coupling various systemcomponents, including database cluster 24, with the control server 22.The system bus may be any of several types of bus structures, includinga memory bus or memory controller, a peripheral bus, and a local bus,using any of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronic Standards Association (VESA) local bus, andPeripheral Component Interconnect (PCI) bus, also known as Mezzaninebus.

The control server 22 typically includes therein, or has access to, avariety of computer-readable media, for instance, database cluster 24.Computer-readable media can be any available media that may be accessedby server 22, and includes volatile and nonvolatile media, as well asremovable and non-removable media. By way of example, and notlimitation, computer-readable media may include computer storage media.Computer storage media may include, without limitation, volatile andnonvolatile media, as well as removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the controlserver 22. By way of example, and not limitation, communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, RF, infrared, and other wirelessmedia. Combinations of any of the above also may be included within thescope of computer-readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 24, provide storage of computer-readableinstructions, data structures, program modules, and other data for thecontrol server 22. The control server 22 may operate in a computernetwork 26 using logical connections to one or more remote computers 28.Remote computers 28 may be located at a variety of locations in amedical or research environment, for example, but not limited to,clinical laboratories (e.g., molecular diagnostic laboratories),hospitals and other inpatient settings, veterinary environments,ambulatory settings, medical billing and financial offices, hospitaladministration settings, home health care environments, and clinicians'offices. Clinicians may include, but are not limited to, a treatingphysician or physicians, specialists such as surgeons, radiologists,cardiologists, and oncologists, emergency medical technicians,physicians' assistants, nurse practitioners, nurses, nurses' aides,pharmacists, dieticians, microbiologists, laboratory experts, laboratorytechnologists, genetic counselors, researchers, veterinarians, students,and the like. The remote computers 28 may also be physically located innon-traditional medical care environments so that the entire health carecommunity may be capable of integration on the network. The remotecomputers 28 may be personal computers, servers, routers, network PCs,peer devices, other common network nodes, or the like, and may includesome or all of the elements described above in relation to the controlserver 22. The devices can be personal digital assistants or other likedevices.

Exemplary computer networks 26 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the control server 22 may include a modem or other meansfor establishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin association with the control server 22, the database cluster 24, orany of the remote computers 28. For example, and not by way oflimitation, various application programs may reside on the memoryassociated with any one or more of the remote computers 28. It will beappreciated by those of ordinary skill in the art that the networkconnections shown are exemplary and other means of establishing acommunications link between the computers (e.g., control server 22 andremote computers 28) may be utilized.

In operation, a clinician may enter commands and information into thecontrol server 22 or convey the commands and information to the controlserver 22 via one or more of the remote computers 28 through inputdevices, such as a keyboard, a pointing device (commonly referred to asa mouse), a trackball, or a touch pad. Other input devices may include,without limitation, microphones, satellite dishes, scanners, or thelike. Commands and information may also be sent directly from a remotehealthcare device to the control server 22. In addition to a monitor,the control server 22 and/or remote computers 28 may include otherperipheral output devices, such as speakers and a printer.

Although many other internal components of the control server 22 and theremote computers 28 are not shown, those of ordinary skill in the artwill appreciate that such components and their interconnection are wellknown. Accordingly, additional details concerning the internalconstruction of the control server 22 and the remote computers 28 arenot further disclosed herein.

Fetal monitoring module 210 may reside on one or more computing devices,such as, for example, computing device 22 described above with referenceto FIG. 1. By way of example only and not limitation, computing devicesmay be a server, personal computer, desktop computer, laptop computer,handheld device, mobile handset, consumer electronic device, or thelike. It should be noted, however, that embodiments are not limited toimplementation on such computing devices, but may be implemented on anya variety of different types of computing devices within the scope ofembodiments thereof.

As previously set forth, embodiments of the present invention related tocomputing systems for monitoring and displaying information regardingthe health of mother and baby during pregnancy, labor and delivery. Withreference to FIG. 2, a block diagram is illustrated that shows anexemplary computing system architecture for displaying and monitoringinformation during pregnancy, labor and delivery. It will be appreciatedthat the computing system architecture shown in FIG. 2 is merely anexample of one suitable computing system and is not intended as havingany dependency or requirement related to any single module/component orcombination of modules/components.

The computing system includes one or more medical devices 205, fetalmonitoring module 210, database 215 and graphical display 220. Discretedata elements are received from device 205. A medical device 205 may beany device, stationary or otherwise, that may be used to treat a patientin a hospital, doctor's office, etc. For exemplary purposes only and notlimitation, medical devices include fetal heart rate monitors, bloodpressure monitors, uterine pressure and contraction activity monitors,blood oxygen saturation monitors, maternal heart rate monitors, othermonitors, ventilators, pumps (e.g., infusion pumps, balloon pumps), apatient's bed, sequential compression devices, electronic securitydevices, and the like.

Database 215 contains a variety of information data for the patient in apatient's electronic medical record (EMR). As utilized herein, theacronym “EMR” is not meant to be limiting, and may broadly refer to anyor all aspects of the patient's medical record rendered in a digitalformat. Generally, the EMR is supported by systems configured toco-ordinate the storage and retrieval of individual records with the aidof computing devices. As such, a variety of types of healthcare-relatedinformation may be stored and accessed in this way. By way of example,the EMR may store one or more of the following types of information:patient demographic; medical history (e.g., examination and progressreports of health and illnesses); medicine and allergylists/immunization status; laboratory test results, radiology images(e.g., X-rays, CTs, MRIs, etc.); evidence-based recommendations forspecific medical conditions; a record of appointments and physician'snotes; billing records; and data received from an associated medicaldevice. Accordingly, systems that employ EMRs reduce medical errors,increase physician efficiency, and reduce costs, as well as promotestandardization of healthcare. Graphical display device 220 may be amonitor, computer screen, project device or other hardware device fordisplaying output capable of displaying graphical user interfaces.

Fetal monitoring module 210 receives and displays data from a medicaldevice for mother and baby during pregnancy, labor and delivery. Fetalmonitoring module 210 may reside on one or more computing devices, suchas, for example, computing device 22 described above with reference toFIG. 1. By way of example, computing device 22 includes a computerprocessor and may be a server, personal computer, desktop computer,laptop computer, handheld device, mobile handset, consumer electronicdevice, or the like.

Fetal monitoring module 210 comprises device data receiving component215, stored information receiving component 230, graphing component 235,receiving component 240, determining component 245 and displayingcomponent 250. Device data receiving component 225, receives discretedata from one or more medical devices 205. It will be appreciated thatwhile fetal monitoring module 210 is depicted as being connected to asingle medical device 225, fetal monitoring module 210 may receivediscrete data from multiple medical devices including medical devicesmonitoring both a mother and her unborn baby.

The data received by data receiving component 225 includes devicerelated output from the medical device. For example, data receivingcomponent 225 may receive data from a fetal heart monitor, a maternalheart monitor, maternal blood pressure monitor, ultrasound, fetal scalpelectrodes and a uterine pressure monitor. In one embodiment, thepatient is continuously monitored and new data points are sent to thedata receiving component 225 such that they may be plotted and displayedin a waveform quickly or in real-time.

Stored information receiving component 230 receives information fromdatabase 215 including a variety of information data for the patient ina patient's electronic medical record (EMR). By way of example, the EMRmay store one or more of the following types of information: annotationsregarding a patient's condition; patient demographic; medical history(e.g., examination and progress reports of health and illnesses);medicine and allergy lists/immunization status; laboratory test results,radiology images (e.g., sonogram, X-rays, CTs, MRIs, etc.);evidence-based recommendations for specific medical conditions; a recordof appointments and physician's notes; billing records; and datareceived from an associated medical device.

Graphing component 235 converts the data received from medical device205 into electronic waveforms that can be displayed as tracings orgraphs. The term waveform refers to the shape of a graph of the varyingquantity against time. Exemplary electronic waveforms for data frommedical devices are shown in FIGS. 6-9. For example, as data comes inindicating a patient's heart rate, it is graphed as function of time ina waveform. In the exemplary waveforms, the newest data is plotted onthe right side of the waveform. The prior data points are to the left ofthe newest plotted point. Exemplary data that is received and may bedisplayed in waveform includes, but is not limited to, fetal bloodoxygenation saturation level, uterine activity, maternal heart rate,maternal EKG data, maternal blood pressure, fetal heart rate (beats perminute) and maternal blood oxygen saturation level. Fetal bloodoxygenation saturation level (FapO2%) may include discrete data elementssuch as oxygenation saturation level, CO2 level, base excess and pH.Uterine activity may include discrete data elements such as uterinepressure and contraction activity of the uterine muscle (mmHG) and maybe measured using tocodynamometry to determine progress of labor.Maternal heart rate is captured as beats per minute. Maternal bloodpressure discrete data elements include systolic blood pressure (mmHG),diastolic blood pressure (mmHG) and mean arterial pressure (mmHG). Fetalheart rate includes beats per minute and may be captured by a monitor,ultrasound, and fetal scalp electrodes. Maternal blood oxygenationsaturation level (SpO2%) may include discrete data elements such asoxygenation saturation level, CO2 level, base excess and pH.

Receiving component 240 receives inputs from a user utilizing acomputing device 220 with a processor such as computing device 22 ofFIG. 1. Receiving component 240 may receive a variety of inputs. Forexample, subcomponents of receiving component 240 receive inputsincluding requests to hide one or more of the waveforms, textualannotations, requests to hide one or more textual annotations, requeststo save snapshots of a particular time period of the waveforms andassociate the snapshots with other files, requests to view alerts,inputs of patient information and a variety of other inputs. Theseinputs will be discussed in more detail below. It will be appreciatedthat receiving component 240 comprises at least one subcomponent and mayhave any number of subcomponents. Alternatively, one or moresubcomponents may be separate receiving components.

Determining component 245 makes a variety of determinations utilizingthe input received by receiving component 210 and may have a number ofsubcomponents. For example, one subcomponent of determining component245 determines to no longer display a waveform on the graphical userinterface if a request to hide the waveform is received. Onesubcomponent of determining component 245 determines to hide annotationsdisplayed if there has been a request to hide an annotation. Anothersubcomponent of determining component 245 determines an area of the oneor more waveforms that is associated with the time of a selectedannotation. It will be appreciated that determining component 245comprises at least one subcomponent and may have a number ofsubcomponents. Alternatively, one or more subcomponents may be separatedetermining components.

Displaying component 250 utilizes a computer processor to display ondisplay device 220 a variety of information. The information displayedregarding the patient's condition may come from medical device 205 anddatabase 215. For example, subcomponents of displaying component 250display graphical user interfaces including information on patientalerts, number of alerts, waveforms for one or more individuals, patientinformation and annotations. It will be appreciated that displayingcomponent 250 comprises at least one subcomponent and may have a numberof subcomponents. Alternatively, one or more subcomponents may beseparate determining components.

Referring next to FIG. 3, a computer-implemented method 300 fordetermining and displaying only requested medical device waveforms forone or more individuals is shown. Computer-implemented method 300 isperformed by one or more computer processors. At step 305, monitoringdata from one or more medical devices for a first individual arereceived. In one embodiment, the first individual is a maternitypatient. Exemplary monitoring data for the maternity patient includesheart rate data from a heart rate monitor, uterine pressure andcontraction information from a uterine pressure and contraction activitymonitor, blood oxygen saturation data from a blood oxygen saturationmonitor(s) and blood pressure from a blood pressure monitor(s).

At step 310, monitoring data from one or more medical devices for asecond individual is received. In one embodiment, the second individualis the unborn baby of the maternity patient. Exemplary monitoring datafor the unborn baby of the maternity patient includes fetal heart ratefrom a fetal heart rate monitor and fetal blood oxygen saturation datafrom a blood oxygen saturation monitor. In one embodiment, the firstindividual may be an unborn baby of a maternity patient and the secondindividual is a second unborn baby of the same maternity patient.

At step 315, the data from the medical devices for the first and secondindividuals is displayed as waveform tracings. Graphing component 235converts the data received from medical device 205 into electronicwaveform tracings that can be displayed by displaying component 250 astracings or graphs. The term waveform refers to the shape of a graph ofthe varying quantity against time. Exemplary electronic waveforms fordata from medical devices are shown in FIGS. 6-9.

At step 320 of FIG. 3, a request to hide one or more of the waveformsdisplayed is received. In one embodiment, a user, such as a nurse ordoctor, may request to hide one or more of the waveforms displayed for afirst individual (e.g., patient, maternity patient or unborn baby ofmaternity patient) and/or second individual (e.g., patient, maternitypatient or unborn baby of maternity patient). For example, and asdiscussed in more detail below, a user may choose to hide a waveformtracing for a maternity patient (e.g., waveform tracing not needed or isinterfering with a waveform being displayed for the unborn baby). Therequest may be a request to hide or alternatively a request to view onlycertain waveforms.

At step 325, it is determined which waveforms to display based on therequest from the user. For example, if the user has requested to viewonly the waveform of one unborn baby from a group of multiple babies,the determining component 245 would determine to display only thewaveform of the one unborn baby and not the waveforms of the otherbabies. In another example, only the waveform tracing(s) of thematernity patient and not the unborn baby may be selected to bedisplayed. At step 330, only the waveforms as determined by determiningcomponent 245 to be displayed are displayed. Furthermore, it will beappreciated that waveform tracings for more than two babies may bedisplayed.

With reference to FIG. 4, a graphical user interface embodied on acomputer-storage media showing data waveforms from one or more medicaldevices is shown. Display 400 includes waveform tracings for a singlematernity patient 405 and her unborn baby. Waveform tracings for fetalheart rate 410, maternal blood pressure 415, maternal heart rate 420 andtocodynamonetry (TOCO) 425. Maternal blood pressure waveform 435,maternal heart rate waveform 420 and maternal uterine pressure andcontraction waveform 425 are displayed for a first individual (maternitypatient) along with fetal heart rate waveform 410 for a secondindividual (unborn baby of maternity patient). Display 400 also includesa display of the most recent numerical value of the data received frommedical devices. Numerical measurements for patient 405 and her unbornbaby for fetal heart rate 430 maternal blood pressure 435 and TOCO 440are displayed on the graphical user interface along with the waveform ofthe data.

For example, with reference to FIGS. 4 and 5, a user has selected inFIG. 4 to hide the waveform 415 for maternal blood pressure as itinterfering with fetal heart rate waveform 410 for which the clinicianwants to see more clearly. The selection is received by receivingcomponent 210 of FIG. 2. It is determined by a subcomponent ofdetermining component 245 that waveform 415 is no longer to bedisplayed. Thus, in graphical user interface 500 of FIG. 5, waveform 415is disabled and displaying component 250 displays the waveforms 410, 420and 425 and not waveform 415.

With reference to FIGS. 6 and 7, graphical user interfaces embodied on acomputer-storage media displaying continuous data waveforms from one ormore medical devices for two or more individuals is shown. Display 600includes waveform tracings for a single maternity patient 605 and herunborn triplet babies 610, 615, and 620. In one example, if one of themultiples appears to be in distress, the clinician may choose to viewonly the waveform of the unborn baby in distress and hide the waveformsfor one or more of the other unborn babies. The selection to hide one ofthe waveforms is received by receiving component 240 of FIG. 2. It isdetermined by determining component 245 that only waveform 615 is to bedisplayed. Thus, waveforms 610 and 620 are disabled and in graphicaluser interface display 700 of FIG. 7 displaying component 250 displaysonly waveform 615 and not waveforms 620 and 625.

Referring next to FIG. 8, a computer-implemented method 800 fordetermining and displaying the area of a medical device waveform for anindividual corresponding to the time of a textual annotation is shown.Computer-implemented method 800 is performed by one or more computerprocessors. At step 805, monitoring data from one or more medicaldevices for a first individual are received. In one embodiment, thefirst individual is a maternity patient. Exemplary monitoring data forthe maternity patient includes heart rate data from a heart ratemonitor, uterine pressure and contraction information from a uterinepressure and contraction activity monitor, blood oxygen saturation datafrom a blood oxygen saturation monitors and blood pressure from a bloodpressure monitors.

At step 810, medical annotations related to the data received from theone or more medical devices is accessed and received. Medicalannotations are accessed from database 215. The medical annotations mayinclude textual notes, comments and observations by a clinicianregarding are variety of things relating to the patient including thepatient's condition, medical history, demographic information, testresults and tasks and examinations performed for the patient. Commonmedical annotations utilized in labor and delivery may be displayed forselection by the clinician. In addition to accessing the medicalannotations, any indication that one or more of the medical annotationsshould not be displayed is also accessed from database 215. The input ofmedical annotations is described below in more detail with reference toFIG. 9. At step 815, it is determined whether any of the annotationsaccessed from database 215 should be hidden. For example, a clinicianmay select to have certain annotations hidden at the time of entry orthereafter.

If it is determined that no annotations have been requested to be hiddenat step 815, all related annotations are displayed at step 818. If it isdetermined that one or more annotations for the patient are to behidden, at step 820, only annotations not identified to be hidden aredisplayed. At step 822, data from the medical devices for the first andsecond individuals is displayed as waveforms. As discussed above, thedata from the medical devices is converted into electronic waveformsthat can be displayed as tracings or graphs.

In one embodiment, at step 825, a user may select one or more of theannotations displayed at steps 820 and 822. The user may choose to viewthe related portion of a waveform tracing for the annotation byselecting or clicking on the annotation. At step 830, the associatedarea of one or more displayed waveforms is determined. For example, ifan annotation was documented as occurring at 8:00 p.m., the area of oneor more of the associated waveform for 8:00 p.m. for the individual isdisplayed. This may be done on a waveform with the most current data orin a separate waveform with historical data. In one embodiment, thecurrent data waveform is displayed simultaneously with a historical datawaveform for the individual and the area. This is described below inmore detail with reference to FIG. 10.

As shown in FIG. 9, an exemplary graphical user interface 900 forallowing a user to input medical annotations for a labor and deliverypatient is shown. As depicted in FIG. 9, the annotation box 905 isdisplayed along with waveform of medical device data for the maternitypatient and unborn baby. Textual annotations may be input by a clinicianinto text box 910. Common medical annotations 915 for labor and deliverythat may be selected by a clinician include, but are not limited to,increase IV fluids, O2 8-10 L/Min per FM, oxytocin infusiondiscontinued, oxytocin infusion increased, primary provider at bedside,primary provider notified, pushing, tocolytic administration, patientturned to left side and vaginal examination. The clinician may selectsign button 925 to send and store any annotations made. The annotationsalong with the associated time and date when the annotation was made arethen stored in database 215.

With regard to FIG. 9, a user, such as a nurse or doctor, may enter orselect an annotation and choose to have it hidden for privacy reasons byselecting check box 1520. For example, sensitive information about thematernity patient, such as past pregnancies, terminated pregnancies,medical conditions (e.g., sexually transmitted diseases) and demographicinformation (e.g., weight) may be selected to be hidden by theclinicians so that non-medical personnel in the patient's room cannotsee the annotations. Non-medical personnel may include persons in anon-medical care giving role such as family and friends of the patientand personnel of the healthcare facility that have no need to know themedical information contained in the annotation. This annotation and theselection to “hide” the annotation are stored in a database, such asdatabase 215.

With reference to FIG. 10, an exemplary graphical user interface 1000for displaying waveform data and related medical annotations for apatient is shown. As depicted in FIG. 10, medical annotations 1005 arein an area on the user interface 1000 separate from the display areas ofcurrent 1015 and historical 1020 waveform tracings for the patient. Thecurrent waveform tracing 1015 has the most recent data for the patientfrom one more medical devices. Historical waveform tracing 1020 hashistorical data for the patient from one or more medical devices for aspecific time period. In this example, the exemplary specific historicaltime period for the patient is from 6 a.m. to 7 a.m. on Oct. 27, 2007.Medical annotations 1005 for the patient are listed from the most recentto the oldest. For example, medical annotation 1010 of maternal bloodpressure and maternal heart rate is the most recent medical annotationfor the patient.

Referring next to FIG. 11, an exemplary graphical user interface 1100for displaying current, historical and archived waveform tracings alongwith medical annotations for a patient is shown. As depicted in FIG. 11,medical annotations 1105 are in an area on the user interface 1100separate from the display areas of current 1120, historical 1125 andarchived 1130 waveform tracings of data for the patient from one or moremedical devices. The time frame on a waveform associated with a selectedmedical annotation is displayed. The current waveform tracing 1120 hasthe most recent data for the patient from one more medical devices onOct. 27, 2007. Historical waveform tracing 1125 has historical data forthe patient from one or more medical devices for a specific time period.In this example, the exemplary specific historical time period for thepatient is from 6 a.m. to 7 a.m. on Oct. 27, 2007 which is an earliertime period of the same visit of the patient as the current 1120waveform tracing. For example, the same visit of the patient may be anadmission to a hospital or a doctor's visit. Archived waveform tracing1130 is for a different visit of the patient on Oct. 13, 2007. In thisexample, the archive view includes annotations 1115 and waveform tracing1130 for a previous hospital admittance or doctor's visit for thepatient.

As described with reference to FIG. 8, a user may select one of theannotations 1110 and 1115 to view the related portion of thecorresponding current 1120, historical 1125 or archived 1130 waveformtracing. For example, if annotation 1110 (made at 8:10 a.m. on Oct. 27,2007) is selected by a user, the associated time period (8:00 to 9:00a.m. on Oct. 27, 2007) on of the historical waveform tracing 1125 isdisplayed. An identification 1135 of the time corresponding to the timeof the annotation (8:10 a.m. on Oct. 27, 2007) is displayed on waveformtracing 1125. If the user selects annotation 1115, the associated timeperiod of the archived annotation is displayed on the archived waveformtracing 1130. An identification 1140 of the time correspondingannotation time is displayed on archived waveform tracing 1130.

Referring next to FIG. 12, a computer-implemented method 1200 fordisplaying patient alert information based on location is shown.Computer-implemented method 1200 is executed by one or more computerprocessors. At step 1205, monitoring data from one or more medicaldevices for a patient is received. In one embodiment, the patient is amaternity patient or an unborn baby. Exemplary monitoring data isdescribed above.

At step 1210, it is determined that the monitoring data receivedsatisfies a rule that would trigger an alert. Exemplary rules includedetermining data for a heart rate is outside of a specified range, apatient's blood pressure outside of a specified range, uterine pressureand contraction data outside of a specified range, blood oxygen levelsoutside of a specified range and other data outside of a specifiedrange. At step 1215, it is determined whether the location of the devicedisplaying patient information is to be alerted. The determination isbased on the physical location of the device and is not dependent onwhich user is logged on or signed into the device. In some instances,based on location of the device, all alerts for all patients are to bedisplayed. For example, a nurse manager may want to see all alerts forall patients. In some instances, based on the location of the displaydevice, all alerts for only some patients are to be displayed. Forexample, if a floor is divided into multiple nursing units, each nursingunit including four patient rooms, only alerts for the patients in thepatient rooms of the nursing unit will be displayed on devices locatedin the nursing unit. In some instances, based on the location of thedisplay device, no alerts are to be displayed and only the number ofalerts is to be displayed. For example, as the caregivers in theoperating or c-section room cannot leave to respond to any alerts, anoperating or c-section room may be designated as a location to displayonly the number of alerts and not the actual alert information.

At step 1220, if it is determined the display device location is not todisplay the content of the alerts; only the number of alerts isdisplayed. Alternatively, no information is displayed. At step 1225, ifit is determined that the display device location is to display thealerts and alert content, the alert, alert content and total number ofcurrent alerts are displayed. In one embodiment, the alert and alertcontent are displayed at the display device location.

Referring next to FIG. 13, an exemplary graphical user interface 1300displaying waveform tracings of monitored data for multiple maternitypatients 1315. Based on the location of the display device beingutilized to display graphical user interface 1300, all alerts for allpatients are displayed. It can be seen in exemplary graphical userinterface 1300 that exemplary patients Anna Long 1320 and Jane Cooper1325 are highlighted and are in alert. In addition, the total number ofalerts 1305 is displayed on the graphical user interface so that a usercan see how many alerts there are and identify necessary personnel toaddress the alerts. In this example, there are a total of two (2) 1310patients in alert. A user may choose to view only waveform tracings forthose patients with alerts. In one embodiment, this is done by selectingalert button 1305.

Referring next to FIG. 14, an exemplary graphical user interface 1400displaying waveform tracings for patients with alerts 1425 is shown.Graphical user interface 1400 includes the waveform tracings forfictitious patient Michelle Bailey 1410 and Anna Long 1415. A user mayselect to suspend, cancel and/or enter a textual annotation 1425 for thepatient regarding the alert from graphical user interface 1400. Thetotal number patients with alerts 1420 is displayed on the graphicaluser interface.

FIG. 15 is an exemplary graphical user interface 1500 allowing a user toflag and store a portion of a waveform tracing 1505. Graphical userinterface 1500 includes multiple waveform tracings for fictitiouspatient Michelle Bailey. A user, such as a nurse or clinician, flags aportion of the waveform tracing 1505. The user may then select toassociate the portion of the waveform tracing 1505 with additionalinformation for the patient such as textual entries, pictures, video,sonogram photographs, sonogram video, laboratory results and otherstored files for the patient that relate to the time period of thewaveform tracing 1505. For example, the portion of the waveform tracing1505 may be for the period while a sonogram was being performed for thepatient.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the scopeof the claims below. Embodiments of our technology have been describedwith the intent to be illustrative rather than restrictive. Alternativeembodiments will become apparent to readers of this disclosure after andbecause of reading it. Alternative means of implementing theaforementioned can be completed without departing from the scope of theclaims below. Certain features and subcombinations are of utility andmay be employed without reference to other features and subcombinationsand are contemplated within the scope of the claims.

The invention claimed is:
 1. Computer storage media havingcomputer-executable instructions embodied thereon that, when executed,cause a computing device to perform a method of displaying on a userdisplay device alarm-triggering events detected by the medical devicebased on a location of the user display device, the method comprising:receiving from a medical device patient data which triggers an alarm;determining a physical location of first and second user displaydevices, wherein the physical location of the first and second userdisplay devices is independent from the users logged onto the first andsecond user display devices; determining that the physical location ofthe first user display device is designated to have the alarm displayed;determining that the physical location of the second user display deviceis not designated to have the alarm displayed; and in response to thedeterminations, displaying the content of the alarm on the first userdisplay device and not the second user display device.
 2. The media ofclaim 1, wherein the patient is a maternity patient and the medicaldevice patient data is for the maternity patient and her unborn baby. 3.The media of claim 2, wherein the first user display device is locatedat a nurse manager's station and the second user display device islocated in an operating room.
 4. The media of claim 2, wherein the firstuser display device is located in a patient's room and the second userdisplay device is located in an operating room.
 5. A computerized methodcarried out by a computing device having one or more processors fordisplaying on a user display device alarm-triggering events detected bythe medical device based on a location of the user display device, themethod comprising: receiving from a medical device patient data whichtriggers an alarm; determining a physical location of first and seconduser display devices, wherein the physical location of the first andsecond user display devices is independent from the users logged ontothe first and second user display devices; determining, using the one ormore processors, that the physical location of the first user displaydevice is designated to have the alarm displayed; determining that thephysical location of the second user display device is not designated tohave the alarm displayed; and in response to the determinations,displaying the content of the alarm on the first user display device andnot the second user display device.
 6. The method of claim 5, whereinthe patient is a maternity patient and the medical device patient datais for the maternity patient and her unborn baby.
 7. The method of claim6, wherein the first user display device is located at a nurse manager'sstation and the second user display device is located in an operatingroom.
 8. The method of claim 6, wherein the first user display device islocated in a patient's room and the second user display device islocated in an operating room.
 9. A system for displaying on a userdisplay device alarm-triggering events detected by the medical devicebased on a location of the user display device, the system comprising: acomputing device having one or more processors and one or morecomputer-storage media; and a data store coupled with the computingdevice, wherein the computing device: receives from a medical devicepatient data which triggers an alarm; determines a physical location offirst and second user display devices, wherein the physical location ofthe first and second user display devices is independent from the userslogged onto the first and second user display devices; determines thatthe physical location of the first user display device is designated tohave the alarm displayed; determines that the physical location of thesecond user display device is not designated to have the alarmdisplayed; and in response to the determinations, displays the contentof the alarm on the first user display device and not the second userdisplay device.
 10. The system of claim 9, wherein the patient is amaternity patient and the medical device patient data is for thematernity patient and her unborn baby.
 11. The system of claim 10,wherein the first user display device is located at a nurse manager'sstation and the second user display device is located in an operatingroom.
 12. The system of claim 11, wherein the first user display deviceis located in a patient's room and the second user display device islocated in an operating room.